-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix trash-bin propfind responses #2821
Conversation
759a870
to
0bb42d2
Compare
@C0rby the root href is now correct. I see things like:
The root entry has href "/remote.php/dav/trash-bin/Alice/" - correct. And folders in the trashbin root have href like "/remote.php/dav/trash-bin/Alice/05bbef6c-6291-4473-92b0-5d9625c5e368/" - looks good. But when the test code them traverses down to PROPFIND the folder in the trashbin, to find its contents:
it correctly lists folder "PARENT/CHILD" and file "PARENT/parent.txt". But it lists "/remote.php/dav/trash-bin/Alice/" - the top-level root of the trashbin. On oC10, a PROPFIND somewhere down in the trashbin lists the element that the propfind request was done on, for example, I expected to see
I haven't tried doing a PROPFIND to "/remote.php/dav/trash-bin/Alice/05bbef6c-6291-4473-92b0-5d9625c5e368/CHILD/" yet - maybe it will work? I can work-around these differences in the test code, but if it can be made consistent with oC10 then it will be even easier, and clients will be able to reliably recurse into the trashbin contents, just like with oC10. |
Ah, yeah this is still a bug here and I'll fix it. Shouldn't be too hard.
This should work IIRC.
No, it definitely should be consistent. I'll try to fix it. 👍 |
Kudos, SonarCloud Quality Gate passed! |
Good stuff. My testing works. I will provide updated test code to revert the previous work-around: |
@C0rby it would be good to fix this in reva master also, then the same test code will pass in the same way. Can you make a PR? |
Fixed the href of the root element in trash-bin propfind responses.
Fixes: owncloud/ocis#1846